Pull requests must include at least one of the required labels: internal (no release notes required), highlight, enhancement, bug, deprecation, documentation. Except for internal, pull requests must also include a description in the release notes section.

Pull requests must include at least one of the required labels: internal (no release notes required), highlight, enhancement, bug, deprecation, documentation. Except for internal, pull requests must also include a description in the release notes section.

Pull requests must include at least one of the required labels: internal (no release notes required), highlight, enhancement, bug, deprecation, documentation. Except for internal, pull requests must also include a description in the release notes section.

Pull requests must include at least one of the required labels: internal (no release notes required), highlight, enhancement, bug, deprecation, documentation. Except for internal, pull requests must also include a description in the release notes section.

Pull requests must include at least one of the required labels: internal (no release notes required), highlight, enhancement, bug, deprecation, documentation. Except for internal, pull requests must also include a description in the release notes section.

Execute training notebooks for PRs

✓ INFO: Live previews are available —

• Open development series
• Open validation series

PR Summary

This pull request introduces several key enhancements and fixes:

1. Deployment Workflows Updates:

   • In the production, staging, and PR preview deployment workflows, the AWS S3 sync commands have been updated to include a cache-control header (--cache-control "no-cache, max-age=0, must-revalidate"). This change ensures that the deployed documentation is always fetched fresh without caching delays.
   • The docs validation workflow now checks out release-notes from a specific branch (nrichers/sc-16263/release-notes-for-26-06), ensuring that the correct release notes are used during deployment.

2. Documentation Template Update:

   • The generated timestamp in the HTML footer of the documentation template has been updated to reflect a new generation date and time.

3. Notebook Enhancements:

   • In one of the test configuration notebooks, the API endpoint has been updated from a localhost URL to a production endpoint (https://app.prod.validmind.ai/api/v1/tracking) and placeholder API credentials have been updated to safer dummy values.
   • A complete new quickstart notebook for model documentation using OIDC device flow has been added. This notebook guides users through an alternative authentication flow (OIDC device authorization flow) and provides a comprehensive walkthrough from setup to running tests and generating documentation.

4. Release Notes Update:

   • The release notes configuration now includes an additional field (subtitle) in the fields array, allowing for more detailed release information.

Overall, these changes improve deployment reliability by enforcing fresh content delivery, enhance documentation clarity, and extend the available authentication options for users.

Test Suggestions

• Verify that the docs deployment workflows (prod, staging, and PR preview) sync files with the expected cache-control headers and trigger CloudFront invalidations correctly.
• Run the validation workflow to ensure that the correct release notes branch is checked out and integrated.
• Execute the updated notebooks to confirm that the API endpoint changes correctly direct to the production environment and that no sensitive credentials are exposed.
• Manually test the new quickstart notebook to validate the OIDC device flow sign-in process and confirm that it properly documents the complete guide.
• Review the rendered documentation from the updated template to ensure the new timestamp and layout changes are correctly applied.

Validate docs site

✓ INFO: A live preview of the docs site is available — Open the preview